Skip to content

Upgrade React from f0dfee38-20260529 to 43bcbf80-20260603#94440

Merged
gnoff merged 8 commits into
canaryfrom
update/react/19.3.0-canary-43bcbf80-20260603
Jun 5, 2026
Merged

Upgrade React from f0dfee38-20260529 to 43bcbf80-20260603#94440
gnoff merged 8 commits into
canaryfrom
update/react/19.3.0-canary-43bcbf80-20260603

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2026

Tests Passed

Commit: 7fb736a

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2026

Stats cancelled

Commit: 7fb736a
View workflow run

@eps1lon eps1lon force-pushed the update/react/19.3.0-canary-43bcbf80-20260603 branch from 546fe9e to c5c5d64 Compare June 4, 2026 05:04
gnoff added 2 commits June 4, 2026 10:36
…task abort will be observed

We now assume the first task is the sync abort task. We have to track if it is cleared in a microtask b/c later onError might observe it when the abort finishes.

I added a test for the unsupported microtask case. We should better support this but currently it is only asserting current behavior.
The assertion was trying to veirfy no /ssg-page-2 chunk was prefetched but on this particular build the ssg-page chunks's name starts with ssg-page-<hash starting with 2> and it collides. upates the assertion to generate the real chunk name
@gnoff gnoff merged commit 84f9247 into canary Jun 5, 2026
241 of 246 checks passed
@gnoff gnoff deleted the update/react/19.3.0-canary-43bcbf80-20260603 branch June 5, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants